This forum is closed to new posts and
responses. Individual names altered for privacy purposes. The information contained in this website is provided for informational purposes only and should not be construed as a forum for customer support requests. Any customer support requests should be directed to the official HCL customer support channels below:
RE: How to decode dxl:itemdata-Elements ~Umberto Nongeroson 21.Jan.03 12:54 AM a Web browser Toolkits All ReleasesAll Platforms
I think this question may have been answered all or in part previously in this forum (I only have a partial replica at the moment and I can't find it, however).
First, I'm going to guess that you're using R5. In 6.0 we corrected a previous shortcoming where file attachments were emitted as <item><itemdata type='3'>... They are now emitted as <item><object><file><filedata>... where the <file> attributes some of its child elements give you information about the file and the <filedata> gives you the actual file content in Base64.
In R5, all of the "metadata" about the file was unfortunately buried in the <itemdata>. This would also be true for any 6.0 constructs that are TYPE_OBJECT (3) but are not files (there are several other types of objects in Notes). For these, a determined programmer can pick apart the <itemdata> which is as follows:
// 1. A WORD containing the item's data length.
// 2. A WORD containing the object's class.
// 3. A WORD containing the object's privilege mask.
// 4. The item data.
// 5. The object data.
The item data will always start with an OBJECT_DESCRIPTOR. Depending on the type of object, additional type-specific data may follow (e.g. FILEOBJECT for a file object). You will find these type definitions in the header files of the C API.
Hope this helps. I only follow this forum as time permits but I will try to check back here for any follow-up.
Return to top
. . RE: How to decode dxl:itemdata-Elem... (~Isaac Quettoog... 21.Jan.03)
Print this page
